Release 1229.0.0 - #10080

…etaMask#45982)

## **Description**

Bump `@metamask/phishing-controller` to `^17.4.1` and
`@metamask/transaction-controller` to `^69.8.0` so the extension picks
up the address-poisoning known-set fix from
[MetaMask/core#9943](MetaMask/core#9943),
published in
[MetaMask/core#10080](MetaMask/core#10080).

### Summary

Ship the controller-side known-recipient cleanup that complements the
confirmation-side gate already merged in
[MetaMask#45724](MetaMask#45724).

### Problem

`PhishingController` was still hydrating known recipients via
`getEffectiveRecipient`, so confirmed approves and other non-sends could
put token/protocol addresses into the comparison set and cause
false-positive lookalike warnings.

### Solution

- Bump `@metamask/phishing-controller` `^17.4.0` → `^17.4.1` (known set
uses `getSendRecipients`)
- Bump `@metamask/transaction-controller` `^69.5.1` → `^69.8.0` (exports
`getSendRecipients`; required by phishing-controller 17.4.1)
- Bump `@metamask/utils` `^11.11.0` → `^11.12.1` to consume the
published ESM fix from
[MetaMask/utils#309](MetaMask/utils#309)
- Import `getSendRecipients` from `@metamask/transaction-controller` and
delete the temporary local copy / tests introduced in MetaMask#45724
- Deduplicate compatible 17.4.x, 69.x, and utils 11.x ranges to a single
copy each

`transaction-controller@69.8.0` depends on `@metamask/utils@^11.12.0`,
so it resolves directly to the fixed 11.12.1 patch release. The
temporary Yarn patch is no longer needed.

The LavaMoat grant allowing `@metamask/utils` to import
`@metamask/scure-bip39` remains necessary because utils 11.12 added that
dependency. Without it, the background cannot start (`Policy does not
allow importing @metamask/scure-bip39 from @metamask/utils`) and E2E
times out on `.controller-loaded`.

No breaking API adaptations required.

### Risk

Low. Additive/non-breaking package bumps plus swapping a local helper
for the published export. The confirmation gate from MetaMask#45724 already
avoids scanning non-send candidates; this bump cleans the in-memory
known set on controller construction. Utils 11.12.1 is a patch release
that corrects ESM module interop without changing mnemonic behavior.

## **Changelog**

CHANGELOG entry: Fixed address-poisoning detection so confirmed token
approves and other non-send transactions no longer seed lookalike
comparisons against token or protocol contract addresses.

## **Related issues**

Fixes:

- Consumes
[MetaMask/core#9943](MetaMask/core#9943)
- Released in
[MetaMask/core#10080](MetaMask/core#10080)
- ESM compatibility fix:
[MetaMask/utils#309](MetaMask/utils#309)
- Follow-up to
[MetaMask#45724](MetaMask#45724)
- Ticket:
[PSAFE-633](https://consensyssoftware.atlassian.net/browse/PSAFE-633)

## **Manual testing steps**

1. Pull this branch, run `yarn install`, and start a development build.
2. On Base, submit and confirm an `approve(Permit2, 0)` against a vanity
token contract (for example Base Uncle). Wait until Activity shows
confirmed.
3. Submit a native send to a lookalike of that token contract address
(same first 4 / last 4 hex characters). Cancel rather than confirming.
4. Confirm no address-poisoning warning appears. On a build pinned to
`phishing-controller@17.4.0`, that send warns because the approve seeded
the token contract into the known set.
5. Confirm a real native send to a new address, then submit a lookalike
of that payee and cancel it. Confirm the address-poisoning warning still
appears for a real prior send payee.

## **Screenshots/Recordings**

See verification artifacts on
[MetaMask/core#9943](MetaMask/core#9943) and
[MetaMask#45724](MetaMask#45724).

### **Before**

Confirmed approve could seed a token contract into the phishing known
set, so a later send to a lookalike of that contract warned.

### **After**

Confirmed approve does not seed the known set; lookalike send against
the token contract does not warn. Real prior send payees still trigger
the warning.

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

[PSAFE-633]:
https://consensyssoftware.atlassian.net/browse/PSAFE-633?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Non-breaking dependency bumps and a straight swap from a duplicated
helper to the published export; behavior change is limited to phishing
known-set population for address-poisoning detection.
> 
> **Overview**
> Upgrades **`@metamask/phishing-controller`** to `^17.4.1`,
**`@metamask/transaction-controller`** to `^69.8.0`, and
**`@metamask/utils`** to `^11.12.1` so address-poisoning known-recipient
hydration uses **`getSendRecipients`** instead of treating
token/protocol addresses from approves and other non-sends as prior
payees.
> 
> The confirmation hook **`useAddressPoisoningAlert`** now imports
**`getSendRecipients`** from `@metamask/transaction-controller`; the
temporary local **`getSendRecipients`** implementation and its unit
tests are removed, with the alert test mocking the package export.
> 
> Sentry masks and the E2E state-log fixture add
**`batchTransactionCounts`** for the transaction controllers introduced
in the bumped **`transaction-controller`** version.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
4ef3cd6. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->